home *** CD-ROM | disk | FTP | other *** search
- Path: etek.chalmers.se!chalmers.se!sunic!mcsun!Germany.EU.net!ira.uka.de!rz.uni-karlsruhe.de!not-for-mail
- From: UKGV@DKAUNI2.BITNET (Dietmar Heidrich)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Memory allocation
- Message-ID: <1kobeq$1na@nz12.rz.uni-karlsruhe.de>
- Date: 3 Feb 93 11:48:42 GMT
- Sender: usenet@nz12.rz.uni-karlsruhe.de
- Organization: University of Karlsruhe, Germany
- Lines: 26
-
- In article <C1uCGL.KnD@unx.sas.com> Doug Walker wrote:
- > MEMF_PUBLIC does not mean anything.
- >
- > It has never meaned anything.
- >
- > It will never mean anything.
- >
- > This is because it is so badly misused that no system VM code could
- > ever take advantage of it. Any VM additions to the OS will not use
- > the MEMF_PUBLIC bit.
-
- I think I am going to correct this statement. Here in Germany a public
- domain VRAM-Manager has been published by M*rkt & T*chn*k that is using
- this bit. Memory allocated with MEMF_PUBLIC is not written to disk
- during swapping. For all programmers, follow this instruction:
-
- Allocate anything except ports and other structures that need to be
- shared by more than one process at the same time WITHOUT MEMF_PUBLIC.
- MEMF_PUBLIC means this piece of memory MUST stay where it is. Memory
- allocated without public status is allowed to be swapped to disk.
- There is also the condition that the memory has to be FASTMEM. CHIP
- memory cannot be swapped.
-
- At least, using MEMF_PUBLIC with care and thought is a good style.
-
- Dietmar Heidrich, Germany